Add a fallback to free GH runners, when there is a problem with the self-hosted ones #1063
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference Issues/PRs
Add a fallback to free GH runners, when there is a problem with the self-hosted ones.
What does this implement or fix?
We have seen that sometimes there are problems with registering a Self-hosted runner in GH.
This problem can persist for an unknown amount of time.
To address this, I am adding a fallback mechanism to start jobs on the free Linux runners for the regular CI and the conda build.
The benchmark builds are not blocking anything and they would take way too long on a free GH runner anyway, so I haven't added the mechanism there.